Talking with @jattasNI put together a more end-to-end prototype that I think shows the pattern more clearly. Instead of having a declarative icon registration and renderer at the same time we will split the registration and rendering into separate parts.

Registration will be a programmatic API call from C#, i.e. a function like RegisterIconDynamicAsync. With the registration complete you have all the pieces you need to render in a table. The PoC PR #2827 shows what calling a registration from C# looks like and how it is used in the table. To take the PoC over the finish line we should move the JSInvoke calls from the example app and into the OkBlazor library. I added some comments about where they should go. In the example we have a helper JS Component with a static method for registering I think we should have a similar helper Blazor Component with a static method for registering. We'd then also want tests in the component, blazor, and storybook docs to finish up.

As a follow-on if you want to use the icons in spots outside the table we can add an addtional helper component to render the icon like <OkIconViewer Icon="ok-dynamic-icon-awesome"></OkIconViewer>. That's only if you also want to render dynamic icons in buttons, dropdowns, etc (the PoC branch linked does not demonstrate the Viewer but my understanding is for today you just need the Table support). The pattern suggested here is to align with the table mapping icon:

<NimbleMappingIcon Icon="ok-dynamic-icon-awesome"></NimbleMappingIcon>
<OkIconViewer Icon="ok-dynamic-icon-awesome"></OkIconViewer>

If the above sounds good and you want to take the PoC branch over the finish line with the above suggestions then we have enough detail captured here to avoid needing the complete HLD.